Search results for "Systems development life cycle"
showing 8 items of 8 documents
An Information Systems Design Product Theory for Software Project Estimation and Measurement Systems
2009
There is relatively little research on software Project Estimation and Measurement Systems (PEMS). Commercial PEMS vary in functionality and effective- ness. Their intended users thus do not know what to ex- pect from PEMS and how to evaluate them. This paper creates an information system design product theory for the class of PEMS that prescribes the meta-requirements, the meta-design, and applicable theories for all products within the class. Meta-requirements and the meta-design are derived from the project estimation and measurement literature, experiences obtained during more than ten years of empirical work in Finnish Software Measurement Association, and a commercially available PEMS.
AMCAS: Advanced Methods for the Co-Design of Complex Adaptive Systems
2006
Abstract This work proposes a new approximation to design and program Complex Adaptive Systems (CAS), these systems comprise neural network, intelligent agents, genetic algorithms, support vector machines and artificial intelligence systems in general. Due to the complexity of such systems, it is necessary to build a design environment able to ease the design work, allowing reusability and easy migration to hardware and/or software. Ptolemy II is used as the base system to simulate and evaluate the designs with different Models of Computation so that an optimum decision about the hardware or software implementation platform can be taken.
Are requirements elicitation sessions influenced by participants' gender? An empirical experiment
2021
[EN] Context: Requirements elicitation is a crucial phase in the software development life cycle. During requirements elicitation sessions, requirements engineers capture software requirements, and motivate stakeholders to express needs and expected software functionalities. In this context, there is a lack of extensive empirical research reporting the extent to which elicitation sessions can be influenced by participants' gender. Objective: This paper presents our research endeavour to investigate requirements engineers' effort and elicited requirements' accuracy based on participants' gender. Method: We conducted an experiment in two rounds with a total of 59 students who played the role …
Explaining Change Paths of Systems and Software Development Practices
2010
This chapter discusses how systems development practices are shaped. Based on interviews conducted in ten development organizations and previous literature, we identify eight types of change paths in systems development practices: emergence, adoption, idealization, formalization, abandonment, informalization, entropy, and disobedience. We argue that the eight change path types provide an integrated theoretical framework on the study of how systems development practices change in organizations, projects, and among individual developers in a given context. We discuss how this framework complements existing theories and concepts of the contemporary literature on systems development.
An Information Systems Design Theory for Integrated Requirements and Release Management Systems
2009
High-tech companies need to collect and analy- ze requirements and allocate them to appropriate product releases in market-driven product development. Develop- ment activities are typically scattered across multiple sites and involve multiple partners in different countries, complicating requirements and release management. Fle- xible, scalable, and secure groupware-based support for the activities provides substantial payoffs. Yet, the extant literature provides little theoretical guidance for designing and using requirements and release management systems in multi-site, multi-partner environments. This article de- velops the meta-requirements and a meta-design of an Information Systems De…
Towards Integrated Computer Aided Systems and Software Engineering Tool for Information Systems Design
1996
The paper starts with a brief overview of the current situation in the world of CASE tools for information systems. Then there follows the outline of the basic ideas and principles of integrated CASE tool GRADE. The most outstanding characteristics of GRADE are that the tool is based on a unified specification language GRAPES and that it supports all information system development phases including analysis, requirements specification, design and implementation.
Towards Practical Cybersecurity Mapping of STRIDE and CWE — a Multi-perspective Approach
2021
Software vulnerabilities are identified during their whole life-cycle; some vulnerabilities may be caused by flaws on the design while other appear due to advances on the technologies around the systems. Frameworks such as OWASP are well- known and are used for testing a systems security before or after implementation, and such testing is carried out against the existing system. Threat modeling however focuses on the early stages of the system design when it is feasible and easy to fix security-related flaws and prevent possible damage caused by them. For example, STRIDE is one very popular threat modeling framework. A STRIDE threat modelling specialist deals with abstract categorizations o…
Domain Specific Case Tool for ICT-Enabled Service Design
2014
One major problem in service design is the limited availability of information gathered during the development process. In particular, information on end-user requirements is difficult for designers, developers, and maintainers to access. Here, we provide a mechanism that supports the gathering and modeling of various types of information throughout the service and software development life cycle. As various existing tools focus on a particular part of the life cycle, essential information is not available, or it is more difficult to obtain in later stages. The linkage between information collected in the different stages is often lost. The implemented tool support enables the modeling of r…